Skip to content

Fix devcontainer CI: drop stale yarn apt source#126

Closed
dev-milos wants to merge 2 commits into
G-Research:mainfrom
dev-milos:fix/devcontainer-bookworm
Closed

Fix devcontainer CI: drop stale yarn apt source#126
dev-milos wants to merge 2 commits into
G-Research:mainfrom
dev-milos:fix/devcontainer-bookworm

Conversation

@dev-milos

@dev-milos dev-milos commented Jun 23, 2026

Copy link
Copy Markdown

Two small fixes so the dev container builds and sets up in CI again (build_test was failing).

@dev-milos dev-milos marked this pull request as ready for review June 23, 2026 13:12
@dev-milos dev-milos marked this pull request as draft June 23, 2026 13:33
The base image (mcr.microsoft.com/devcontainers/ruby:1-3.3-bullseye) ships a
yarn apt source whose signing key was rotated (NO_PUBKEY 62D54FD4003F6525),
so apt-get update fails during the dev container build in CI. Remove that
source before apt-get update; yarn is already installed in the base image.

(Bumping the base image to bookworm does not help: it ships the same source.)
@dev-milos dev-milos force-pushed the fix/devcontainer-bookworm branch from 4bff005 to e339a05 Compare June 23, 2026 13:36
@dev-milos dev-milos changed the title Fix devcontainer CI: bump base image bullseye → bookworm Fix devcontainer CI: drop stale yarn apt source Jun 23, 2026
@dev-milos dev-milos marked this pull request as ready for review June 24, 2026 10:20
@pavlovic-ivan pavlovic-ivan requested a review from suprjinx June 24, 2026 10:24
The postCreateCommand calls rake directly, which resolves the system
rake (13.4.2) instead of the bundled one (Gemfile: 13.2.1), causing
Gem::LoadError during dev container setup. Run rake through bundle exec.
@dev-milos

Copy link
Copy Markdown
Author

Note: flagged the remaining failure with the maintainer on Slack.

This PR fixes two of the devcontainer-CI failures - the base image's stale yarn apt source (broke apt-get update) and rake needing bundle exec in postCreateCommand.

CI now gets through both and reaches rake db:setup, which fails with could not translate host name "db": under devcontainers/ci the db service isn't started (the app service has no depends_on, so only app comes up). That last layer is a devcontainer/compose orchestration decision, so leaving it for the maintainers - discussing the best approach (e.g. depends_on + readiness wait) on Slack.

@ivan-pavlovic @suprjinx

@dev-milos dev-milos closed this Jun 25, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant